We are in the process of deploying MBAM in our environment. We had a test server up and functional. When we deployed the web roles to a production server, we now get the error described here: http://support.microsoft.com/kb/2620280 - Error message "An error has occurred" when you click the Hardware tab in MBAM We edited the web.config file per the instructions in the KB article but the problem persists. We did not have to edit the web.config file on our test machine. The main difference between our test web server and production test server is the production web server hosts 7 web sites, the test server was a dedicated web server. The production server web site has an assigned IP address and host header. Another difference is that the test server has IPv6 disabled via the registry, the production machine has IPv6 disabled in the network interface properties. Both test and production Web and DB servers are running Windows Server 2008 R2 with SP1. The database servers are both using SQL Server 2008 R2 Enterprise RTM. We have double-checked permissions and passwords on the servers, both sets configured identically except for what's listed above. A specific question that someone may be able to answer is when editing the web.config file, is there a requirement for entering the servers Computername, vs entering the Cname being used in case we want to load balance later? We've tried both in the web.config file, both failed. The instruction in the KB just says "replace localhost with yourservername." TIA, Tom

Hi, The main cause for this issue is MBAM server cannot access the http://localhost/MBAMAdministrationService/AdministrationService.svc. So first you need to make sure you can resolve the localhost or Computername on MBAM server. Second, check whether you can access the address above. Juke Chou TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.Juke Chou TechNet Community Support

Hi Juke, The URL does not work on the server. We believe this is because another website running on the server uses localhost as its host header. Also, replacing localhost with the DNS FQDN of the website (mbam.mydomain.com) forces a local administrator to enter credentials three times, then gives a 401 access denied error. The odd thing is we can get to the Administration Service service site from any other machine using this URL without any prompt for credentials. We then tried the URL on our test machine console (using mbamtest.mydomain.com), and it gave us the same result - asks for credentials three times, then returns a 401 access denied error. Here we can enter the same URL from any machine other than server and access the AdministrationService service page without being prompted for credentials. What's next? Tom

Additional information. If browsing the Hardware page from IIS Manager on the MBAM server, this is what is returned: Server Error in '/' Application. The remote server returned an error: (401) Unauthorized. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Net.WebException: The remote server returned an error: (401) Unauthorized. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [WebException: The remote server returned an error: (401) Unauthorized.] System.Net.HttpWebRequest.GetResponse() +1126 System.ServiceModel.Channels.HttpChannelRequest.WaitForReply(TimeSpan timeout) +81 [MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'.] System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +10260714 System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +539 Microsoft.Mbam.AdministrationWebsite.AdminServiceReference.IAdministrationService.GetMachineTypes(MachineType type) +0 Microsoft.Mbam.AdministrationWebsite.HardwareController.GetMachineTypes(MachineType type, MachineType[]& machines) +720 Microsoft.Mbam.AdministrationWebsite.Hardware.PopulateHardwareList(String sortExpression, SortDirection sortDirection) +91 Microsoft.Mbam.AdministrationWebsite.Hardware.Page_Load(Object sender, EventArgs e) +701 System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +25 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +42 System.Web.UI.Control.OnLoad(EventArgs e) +132 System.Web.UI.Control.LoadRecursive() +66 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2428 Version Information: Microsoft .NET Framework Version:2.0.50727.5456; ASP.NET Version:2.0.50727.5456 Does this help or just muddy the waters? Tom

Hi, Please check your authentication setting for this site. The odd thing is we can get to the Administration Service service site from any other machine using this URL without any prompt for credentials. What kind of user is used for logon on this computer?Juke Chou TechNet Community Support

Hi Juke, There were two accounts used to test. One was a domain admin in a child domain that is a member of the MBAM server's local administrators group. The second was a domain admin from the domain in which the MBAM server resides. Both accounts get the same results. Tom

I would suggest that you can create a new post in IIS forum since the error is related with the IIS.Thanks Zero Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Update - to get MBAM to work, we had to spin-up new virtual servers and do a fresh install with no other web sites placed on the IIS server. I don't know whether it was MBAM that did not want to coexist with other websites, or one of the other websites did not want to coexist with MBAM. We reused the production SQL Server back-end. Hope this helps someone save some time, Tom